|
|
|
BlueCielo Publisher 2012 Administrator's Guide | BlueCielo ECM Solutions |
Configuration of the Legacy system link relies on installation of the legacy publishing module that is to be used.
Note Properties that are specified in the legacy publishing module configuration file but that do not exist in the destination system are created automatically but must be mapped manually.
To install a legacy publishing module for use with the Legacy system link:
regsvr32 <file name>.dll
Note On 64-bit computers, use the 32-bit version of Register Server as in the following example.
"%SystemRoot%\SysWOW64\regsvr32.exe" <file name>.dll
Note On 64-bit computers, use the 32-bit version of Register Server as in the following example.
"%SystemRoot%\SysWOW64\regsvr32.exe" import <file name>.reg
If a registry file is not available, add a subkey to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\Exporter\Publish Engines
The name of the key is the full COM Program ID like PublisherProject.PublishClass. The default value of the key is a string that contains the description of the publishing module.
Note On 64-bit computers, the module must be registered under:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cyco\Exporter\Publish Engines
To configure a legacy publishing module:
Note If the Legacy system link is installed on a 64-bit computer, the 32-bit version of Dex.exe (Dex32.exe) is also installed to host the 32-bit legacy publishing modules. The 32-bit version must be specified in the applicable scheduled tasks, batch files, and so on.
Related concepts
Copyright © 2000-2014 BlueCielo ECM Solutions |